Business operating system engine

ABSTRACT

An engine for resolving a query from a user to provide a dynamic actionable dashboard in a business operating system includes an MLET database, a data interface, a logic configured to process incoming queries, fetch data in relation to those queries, and render an actionable dashboard having data resulting from the queries. The MLET database comprises a plurality of templates (“MLETs”), each MLET being associated with a unique identifier and including a mechanism for accessing data relating to that identifier. The logic processes queries into constructs having a tokens and configurable inputs. If the query includes a unique identifier associated with an MLET in the MLET database, the MLET is used to fetch data responding to the query. If the query includes a unique identifier not associated with an MLET in the MLET database, the logic creates a new MLET using operational intelligence and stores it in the MLET database.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to and the benefit of U.S. ProvisionalPatent Application No. 62/699,430, filed Jul. 17, 2018, the entirecontent of which is incorporated by reference herein.

BACKGROUND

The present disclosure generally relates to the field of businessoperating systems and specifically to an engine for resolving queries toprovide a dynamic actionable dashboard in a business operating system.

To maintain a competitive advantage, businesses are constantly migratingtheir operations to new and improved technologies. Often, businesses usemultiple systems for different tasks and operations. These systems,however, lack integration and cohesion, which greatly reducesefficiency, a prevent businesses from reaching peak operationalexcellence. While attempts have been made to create business operatingsystems that provide control and coordination over disparate systems,current systems suffer from many drawbacks. For example, existingbusiness operating systems fail to provide visibility and control overthe strategies executed by employees, instead providing only an overviewof performance, based on key result areas at an organizational level.Accordingly, most executives spend their time analyzing and addressingbusiness challenges without identifying the root causes for failing tomeet business goals. Specifically, these business operating systems lackoperational intelligence, and without operational intelligence,executives find it difficult to correlate between the executedstrategies and the strategies of the organization that lead tooperational excellence and efficiency.

Furthermore, existing business operating systems require developers toupdate the framework if any changes related to the goals, targets,employees, roles, and strategies, are made in the organization. Thesechanges to the framework of the business operating system are iterativeand redundant, resulting in inefficient consumption of time andresources. For example, in existing systems, to add a new data model tothe system requires a data team to convert the model to software, totest it and to obtain user acceptance. This process often takes three ormore weeks to complete and must be repeated for each new change. Thissoftware development latency proves untenable in fast-paced businessenvironments.

Accordingly, there is a need for a business operating system thatfacilitates achieving operational excellence and efficiency by providingenterprise-wide visibility and control over the executed strategies.There is a need for a business operating system that helps anorganization adapt to changes in real time. Furthermore, there is a needfor a business operating system that does not require developers toupdate the framework when changes are made to the organizationalhierarchy, goals, targets, employees, roles or strategies of theorganization.

SUMMARY

According to an embodiment, an engine for resolving a query from a userto provide a dynamic actionable dashboard in a business operating systemincludes an MLET database, a data interface, a logic configured toprocess incoming queries, fetch data in relation to those queries, andrender an actionable dashboard having data resulting from the queries.The MLET database comprises a plurality of templates (each an “MLET”),each MLET being associated with a unique identifier and including amechanism for accessing data relating to that identifier. The logicprocesses incoming queries by parsing the query to create an MLETconstruct having a token denoting that that the construct is an MLETconstruct and configurable inputs. The logic further interprets theparsed query to determine whether it includes a unique identifierassociated with an MLET in the MLET database. If the query includes aunique identifier associated with an MLET in the MLET database, thelogic uses the MLET in the MLET database the to fetch data responding tothe query. If the query includes a unique identifier not associated withan MLET in the MLET database, the logic creates a new MLET associatedwith the unique identifier using operational intelligence and stores thenew MLET in the MLET database.

According to another embodiment, a method for resolving a query from auser to provide a dynamic actionable dashboard in a business operatingsystem includes parsing the query to create a template (“MLET”)construct having a token denoting that that the construct is an MLETconstruct and configurable inputs and interpreting the parsed query todetermine whether it includes a unique identifier associated with anMLET in a database of MLETs. If the query includes a unique identifierassociated with an MLET in the MLET database, the method uses the MLETin the MLET database to fetch data responding to the query. If the queryincludes a unique identifier not associated with an MLET in the MLETdatabase, the method creates a new MLET associated with the uniqueidentifier using operational intelligence and stores the new MLET in theMLET database. The method renders an actionable dashboard containing thefetched data.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is schematic diagram of an exemplary MLET engine.

FIG. 2 is a flowchart for an exemplary MLET engine logic.

FIG. 3 is a screenshot of an exemplary query entry form.

FIG. 4 is a flowchart of an exemplary logic for retrieving data via theMLET engine.

FIG. 5 is a screenshot of an exemplary dynamic actionable dashboardaccording to the disclosure.

FIG. 6 is an exemplary business system utilizing the exemplary MLETengine disclosed herein.

DETAILED DESCRIPTION

This Detailed Description merely describes exemplary embodiments of theinvention and is not intended to limit the scope of the claims in anyway. Indeed, the invention as claimed is broader than the exemplaryembodiments, and the terms used in the claims have their full ordinarymeaning, unless an express definition is provided herein.

The present application discloses systems and methods relating to anengine for resolving queries to provide a dynamic actionable dashboardin a business operating system. An exemplary business operating systemcapable of using the presently disclosed system and method is disclosedin U.S. Patent Application Publication No. 2017/0213169 A1 entitled“Social Networking System for Organizational Management,” which isincorporated by reference in its entirety herein. The present system andmethod includes a specific “no-developer-needed” (“NDN”) languageframework and engine that allows non-technical user to quickly make thesame type of organizational changes to a business operating system thatwould typically require a team of data experts several weeks tocomplete. For purposes of this disclosure, the novel engine is referredto a matrixLET (“MLET”) engine. Components of an exemplary MLET engine100 are depicted in FIG. 1.

The exemplary MLET engine includes an MLET database 102. As described inmore detail below, the MLET database 102 stores a set of MLETs, whichare essentially templates having an identifier or acronym defining theMLET, and a mechanism for accessing data associated with that acronym.For example, the MLET may contain a subroutine, such as a webhook, thatis configured to fetch data from databases associated with the MLET. Inanother example, the MLET may include structure query language (SQL)code for accessing a one or more big data or structured data sources. Insome embodiments, the MLET database also includes HTML data associatedwith each MLET that can be quickly returned by the MLET engine forqueries relating to certain MLETS.

The exemplary MLET engine 100 also includes an input/output interface104. The input/output interface 104 serves at least three importantfunctions. First, the input/output interface 104 connects with abusiness operating system or other program to accept queries from a useras described below. The interface 104 for this purpose may take the formof an application programming interface (“API”), and the connectionbetween the MLET engine 100 and the software providing the query may bea local or remote connection, e.g., over the Internet. The input/outputinterface 104 also may connect with external databases to fetch data inresponse to queries. For example, the interface 104 may be an OpenDatabase Connectivity (“ODBC”) connection and may be connected todatabases on the same physical machine as the MLET engine 100, on adifferent machine on the same local network, or at remote locations.Finally, the input/output interface 104 connects to with the businessoperating system or other software to provide result that can be postedto an actionable dashboard or some other display. The results may beprovided through the same or a different API as used for the queries.

The exemplary MLET engine 100 also includes a logic 106. The logic 106may be stored in local or remote memory and used to process incomingqueries, fetch data in relation to those queries, and provide results. Adetailed explanation of the algorithms that that drive the logic 106follows in the flowcharts of FIGS. 2 and 4.

FIG. 2 depicts an overview of a method for processing quires to updatean actionable dashboard. At step 210, a user enters a plain text query.An exemplary form for entering a plain text query is shown in FIG. 3.The form 300 includes a query name field 302 for naming the query. Thequery name field 302 is allows a user (or another user) to easily recallthe query at a later time and provides an identifier for an MLET. Theform 300 further includes a query text field 304, wherein a user entersa plain text query. In the exemplary form 300, a user has queried for agraph of a cycle plan for decision tickets by status. The form 300 alsoincludes a parameters field 306, where by a user can enter any number ofparameters to be considered with the query. For example, the exemplaryform 300 lists a date period, a data filter and an XREF (discussedlater). Possible other parameters include, for example, the type ofdisplay required for the result (e.g., a chart or graph). The form 300also includes a Configuration ID field 308 wherein a user can select aunique number for the saved MLET that assists the system in listingpossible MLETs for a next subsequent use. The form 300 additionallyincludes fields for identifying and grouping the query, such as thedescription field 310 and “where is it used?” field 312. The exemplaryform 300 further includes an HTML Text field 314 to allow the formattingof the information being output from the MLET. Pre-supplied HTMLformatting ensures that the result of an MLET query is formatted andpresented in a way that makes sense to the user, and also allows forfaster retrieval of results, as explained further below. In the form300, the HTML Text field 314 includes code to create a chart using thedata.

FIG. 3 is only one exemplary way of submitting a query. It is alsocontemplated that a user can submit a query using avoice/speech-interface, a chat interface, or a different graphical userinterface on a mobile device or personal computer.

Returning to FIG. 2, as step 220, the system parses the query into anMLET construct with a token. For example, if a user submitted the query“what are the profits made by the organization from a Client XYZ in themonth of November,” the system would parse the query into $[MLET!Profits! CONFIG: Client: XYZ CONFIG: Month: November!], where “$[” isthe token, “Profits” is the MLET, and “client” and “month” areconfigurable inputs. The token helps the MLET engine parse the contentsof the construct to perform operations in accordance with the identifiedMLET. In any document when the system sees the token, it knows that thefollowing text is an MLET statement. The system will parse everythinguntil the “]” and use the parsed text for the MLET query. Theconfigurable inputs filter and/or narrow the scope of the query.

At step 225, the system uses artificial intelligence (e.g., machinelearning) to make interpretations of the parsed query. There is no wayto list or store all possible user queries, so instead, when there aregaps in the reference data for interpreting the queries, the system willdecipher a right answer to the question based on a set of high levelfactors. Such factors include, for example: (1) The user's role,position and/or access permissions, (2) the user's department, (3) theuser's location and/or time-zone, (4) the user's historical querytrends, (5) queries of other users similar to the user, and/or (6)trending queries across all users. In one embodiment, the machinelearning utilizes an algorithm designed to solve the multi-armed banditproblem, for example the epsilon-greedy strategy, epsilon-first strategyor epsilon-decreasing strategy. Other neural networks might be tried todetermine a good fit for predicting the results based on the questionsasked. If the system is still unable to interpret the query, it may senda message to the user stating the it was unable to parse the queryand/or requesting further clarification.

In step 230, the MLET engine determines whether the MLET parsed in step220 and interpreted in step 225 is present in the MLET database. If theMLET engine determines that the MLET is not in the MLET database, thenthe MLET engine creates a new MLET. The new MLET will be associated withdata using operational intelligence. For example, in a case where“profit” is not in the MLET database (or training data), but “grossmargin” is, the system will map profit to be the same as gross margin,and use the same MLET. If the system is not able to make thisdetermination, it will request the user or an administrator to make thatconnection manually in the system. Accordingly, the system becomesincreasingly intelligent about an organization over time. The processfor creating new MLETs is described in more detail below.

If the MLET engine determines that the MLET parsed in step 220 is in theMLET database, then method proceeds to step 240, where it retrieves datacorresponding to the MLET and configurable inputs parsed from the query.In one embodiment, for example, the MLET calls a subroutine, such as awebhook, to retrieve the data from one or more databases. FIG. 4illustrates exemplary aspects if step 240 in greater detail, at step402, the parsed query is submitted to the MLET engine. At step 404, theMLET engine queries the MLET database to determine whether the MLETexists in the MLET database. At step 404, the MLET engine determineswhether the configurable inputs are service level agreement targetnumbers or color text. If so, the engine proceeds to step 406, where itimmediately returns the associated data. This allows the system to savetime by avoiding use of AI resources for queries that have already beendetermined in the past.

If the configurable inputs are not service level agreement targetnumbers or color text, then the engine proceeds to step 408, where itdetermines, based on the MLET, whether the data sought is stored as HTML(or HTM) in the MLET database, or whether the engine needs to queryanother data source for the data. If the data is stored as HTML (or HTM)in the MLET database, for example, in an HTML column, then the engineproceeds to step 410, where it returns the HTML result as stored. Forexample, an MLET may be provided with pre-stored HTML as explained abovewith reference to FIG. 3.

If the data is not stored as HTML in the MLET database, the MLET engineproceeds to step 412, where it determines whether a data query is storedwith the MLET. The query data is a mapping of the terms of the querythat allows the query to run without further interpretation even ifdifferent parameters and filters are used in the query compared toprevious queries. If a data query is stored with the MLET, then thatquery is called and the MLET engine proceeds to step 420. If a dataquery is not stored, then the MLET engine proceeds to step 414, where itbuilds a query. The system keeps a list of query configuration codes(i.e. mappings) stored in the MLET database 102 that may be learned,through use of the system, or pre-stored. The system uses these mappingsto build an appropriate query based on the question presented by theuser. The query may be directed to one or more data sources, forexample, a business operating system database or a timesheet.

At step 418, based on the query submitted from either step 412 or 414,it is determined whether the data sought is in the form of a data arrayof not. If the data is not in the form of a data array, then the MLETengine proceeds to step 420, where it determines whether an HTML columnexists at the data source for the sought data. If an HTML column doesnot exist, then, at step 422, the value for the data stored in thedatabase is returned. If an HTML column does exist, then at step 424 thevalue for the data stored in the database is inserted into a placeholderof the HTML column, the combined HTML is returned.

At step 430, if the data sought is a data array, then the MLETdetermines whether one of the configurable inputs of the original querywas a defined chart type, such as a pie chart, bar chart, histogram,line graph, area chart, etc. If the query included a defined chart type,then at step 432, the MLET engine returns the data array in a chart ofthe requested type. If the query did not include a defined chart type,then the MLET engine proceeds to step 434, where it determines whetheran HTML column exists at the data source for the sought data array. Ifan HTML column does exist, then at step 436, the data array is returnedas a table within the stored HTML. If an HTML column does not exist,then, at step 438, the data is returned as text. The text may bereturned using, for example JavaScript Object Notation (“JSON”), and mayinclude chart data using JavaScript charts such as AMChart or HighChart.

At step 250, the retrieved data is rendered to an actionable dashboard.In one embodiment, the actionable dashboard is an “XFLAT.” And XFLAT isan MLET type that represents information in the form of an annual planversus actual achievements. This can be represented as monthly orquarterly numbers. An exemplary XFLAT 500 is depicted in FIG. 5.

In one embodiment, the system further includes special type of MLETcalled an XREF. The XREF, which can be called using the format $[XREF],does not get data from a database but from other forms or files of thebusiness. For example, a company may have created a mission statementthat is used repeatedly throughout different reports and materials. Ifthe statement needs to be changed, rather than having to change eachinstance separately, with XREF it can be change in one place, and thatchange will propagate to all files that call the $[XREF].

FIG. 6 depicts an exemplary business system 600 that utilizes thedisclosed systems and methods to integrate with a business operatingsystem. In the exemplary system 600, the business operating system OXZion is provided with a data from a set of disparate sources (e.g.,databases, spreadsheets, text files and/or postscript documents). Thedata is fed to the business operating system through an ETL (extract,transfer and load) interface. The query and MLET systems and methodsdescribed above are then used to obtain meaningful results from thedata.

As illustrated in FIG. 6, output data may be provided in many differentforms. For example, based on the results returned and the keyresponsibility area and the SLA of the measure being reviewed by theMLET question, the results can be processed by the business operatingsystem to trigger or modify a specific set of tasks. Tasks can be toautomatically assign, remove, or modify, in relation to variousdepartments and employees within a department of an organization. By wayof example, if the business operating system determines from a queryresult that certain high-priority goals are not being met in onedepartment, while another department has excess resources, the systemcan reassign those tasks to optimize business efficiency. This processhelps ensure that the organization goals are met.

While the above disclosure focuses mainly on display of results, e.g.,through a visual interface of a business operating system, it is furthercontemplating that MLET query results can be pushed to any deviceremotely connected to the business operating system, including theInternet of Things. Exemplary device that can be controlled by MLETresults through a business operating system include smart speakers,smart lamps, virtual assistants, mobile devices, cameras, utilities,appliances, and more.

Some of the steps, acts, and other processes and portions of processesare described herein as being done “automatically.” In the alternative,or in addition thereto, those steps, acts, and other processes andportions of processes can be done with one or more intervening humanacts or other manual acts that eventually trigger the mentioned step(s),act(s), and/or other process(es) and/or process portion(s).

While the present invention has been illustrated by the description ofembodiments thereof, and while the embodiments have been described inconsiderable detail, it is not the intention of the applicants torestrict or in any way limit the scope of the invention to such details.Additional advantages and modifications will readily appear to thoseskilled in the art. Accordingly, departures may be made from suchdetails without departing from the spirit or scope of the applicant'sgeneral inventive concept.

What is claimed is:
 1. An engine for resolving a query from a user toprovide a dynamic actionable dashboard in a business operating system,comprising: an MLET database; a data interface; and a logic configuredto process incoming queries, fetch data in relation to those queries,and render an actionable dashboard having data resulting from thequeries, wherein the MLET database comprises a plurality of templates(each an “MLET”), each MLET being associated with a unique identifierand including a mechanism for accessing data relating to thatidentifier, and wherein the logic processes incoming queries by parsingthe query to create an MLET construct having a token denoting that thatthe construct is an MLET construct and configurable inputs, interpretingthe parsed query to determine whether it includes a unique identifierassociated with an MLET in the MLET database, if the query includes aunique identifier associated with an MLET in the MLET database, usingthe MLET in the MLET database the to fetch data responding to the query,and if the query includes a unique identifier not associated with anMLET in the MLET database, creating a new MLET associated with theunique identifier using operational intelligence and storing the newMLET in the MLET database.
 2. The engine of claim 1, wherein theinterpreting the parsed query is performed using machine learning basedon one of (1) the user's business role, (2) the user's businessdepartment, (3) the user's location (4) the user's historical querytrends, (5) queries of other users similar to the user, and (6) trendingqueries across all users to determine.
 3. The engine of claim 1, whereinthe interpreting the parsed query is performed using a one-armed banditproblem algorithm.
 4. The engine of claim 1, wherein if the configurableinputs comprise a service level agreement, the engine immediatelyreturns data associated with the service level agreement.
 5. The engineof claim 1, wherein if the configurable inputs comprise color text, theengine immediately returns data associated with the color text.
 6. Theengine of claim 1, wherein the logic fetching data comprises determiningwhether the data sought by the query is markup language data and, if so,returning the markup language data as stored.
 7. The engine of claim 1,wherein if the MLET includes a data query, the data query is used tofetch resulting data.
 8. The engine of claim 1, wherein if the MLET doesnot include a data query, the engine builds a data query based onpre-stored mappings and uses the built data query to fetch resultingdata.
 9. The engine of claim 1, wherein the logic fetching datacomprises determining whether the data sought by the query is markuplanguage data and, if not, returning the data as text.
 10. The engine ofclaim 1, wherein the actionable dashboard depicts comparison of anannual plan and actual achievement.
 11. A method for resolving a queryfrom a user to provide a dynamic actionable dashboard in a businessoperating system, comprising: parsing the query to create a template(“MLET”) construct having a token denoting that that the construct is anMLET construct and configurable inputs; interpreting the parsed query todetermine whether it includes a unique identifier associated with anMLET in a database of MLETs; if the query includes a unique identifierassociated with an MLET in the MLET database, using the MLET in the MLETdatabase to fetch data responding to the query; if the query includes aunique identifier not associated with an MLET in the MLET database,creating a new MLET associated with the unique identifier usingoperational intelligence and storing the new MLET in the MLET database;rendering an actionable dashboard containing the fetched data.
 12. Themethod of claim 11, wherein the interpreting the parsed query isperformed using machine learning based on one of (1) the user's businessrole, (2) the user's business department, (3) the user's location (4)the user's historical query trends, (5) queries of other users similarto the user, and (6) trending queries across all users to determine. 13.The method of claim 11, wherein the interpreting the parsed query isperformed using a multi-armed bandit algorithm.
 14. The method of claim11, wherein if the configurable inputs comprise a service levelagreement, the method immediately returns data associated with theservice level agreement.
 15. The method of claim 11, wherein if theconfigurable inputs comprise color text, the method immediately returnsdata associated with the color text.
 16. The method of claim 11, whereinthe fetching data comprises determining whether the data sought by thequery is markup language data and, if so, returning the markup languagedata as stored.
 17. The method of claim 11, wherein if the MLET includesa data query, the data query is used to fetch resulting data.
 18. Themethod of claim 11, wherein if the MLET does not include a data query,the method further comprises building a data query based on pre-storedmappings and using the built data query to fetch resulting data.
 19. Themethod of claim 11, wherein the fetching data comprises determiningwhether the data sought by the query is markup language data and, ifnot, returning the data as text.
 20. The method of claim 1, wherein theactionable dashboard depicts comparison of an annual plan and actualachievement.